Systems and methods for creating a customized watch face and retrieving the watch face to be displayed

ABSTRACT

Systems and methods to create a customized watch face and retrieve the watch face to be displayed are disclosed. Exemplary implementations may effectuate presentation of a selection interface; receive a mint request to mint the watch face in accordance with a watch face design; effectuate a transfer of consideration from a user wallet to an administrative wallet; mint the watch face; transfer a non-fungible token to the user wallet; receive a display request to display the watch face on a watch screen; determine whether the user wallet holds a non-fungible token associated with the watch face; responsive to the user wallet holding the non-fungible token, facilitate display of the watch face on the watch screen; responsive to the user wallet not holding the non-fungible token, take no action to facilitate display of the watch face on the watch screen; and/or perform other operations.

FIELD OF THE DISCLOSURE

The present disclosure relates to creating and/or retrieving acustomized watch face to be displayed on a watch screen.

BACKGROUND

Smartwatches configured to display visual content are known. Watch facescapable of being displayed on smartwatches are known. Distributedledgers are known techniques to produce a secure record or registry ofownership of assets, transactions, and other information. For example, adistributed blockchain is a distributed ledger. Different types ofdistributed ledgers are known.

SUMMARY

One aspect of the present disclosure relates to a system configured tocreate a customized watch face that is capable of being displayed on awatch screen (e.g., of a smart watch). The user may select watch facefeatures with varying styles, formats, colors, and/or other aspectsthrough a selection interface. For example, the user may select aparticular style of hour makers, hour hands, minute hands, and/or otherfeatures to be included in the customized watch face. The values ofwatch face features selected by the user may define a watch face designthat is later used to generate the watch face. The user may purchase thecustomized watch face design by submitting a mint request andtransferring the appropriate amount of consideration from a user walletto an administrative wallet. The transfer of consideration from the userwallet to an administrative wallet may include the transfer of valuefrom an address associated with the user wallet to an address associatedwith the administrative wallet on a decentralized ledger. Onceconsideration is received by the administrative wallet, the watch facecapable of being displayed may be minted and the watch face may containthe values of watch face features defined by the watch face designpurchased by the user. A watch face record may be generated for theminted watch face and a non-fungible token may be transferred to theaddress on the decentralized ledger that corresponds to the user wallet.The watch face record may include information pertaining to the watchface features and may include a watch face identifier that is unique tothe watch face. The non-fungible token may indicate the watch faceidentifier, such that holding the non-fungible token indicates ownershipof the watch face associated to the watch face identifier.

The system is further configured to retrieve the watch face to bedisplayed on a watch screen. The system may receive a display requestfrom a user. The display request may indicate the watch face beingrequested (e.g., using the watch face identifier), the user associatedwith the watch screen, and/or other information. Responsive to receivingthe display request, the system may determine whether the user walletassociated with the user holds a non-fungible token associated with thewatch face being requested. Holding the non-fungible token may indicatethe non-fungible token is recorded on the decentralized ledger at theaddress associated with the user wallet. Responsive to determining theuser wallet holding the non-fungible token, the system may facilitatetransmission of information to the watch screen that causes the watchscreen to display the watch face. Responsive to determining the userwallet does not hold the non-fungible token, the system may take nofurther action to transmit information to the watch screen.

The system configured to create a watch face and retrieve the watch faceto be displayed may include one or more of servers, decentralized ledgerservers, client computing platforms, external resources, networks,users, user interfaces, and or other components. The one or more serversand/or decentralized ledger servers may include electronic storage, oneor more hardware processors, one or more blockchains, and/or othercomponents. The electronic storage may be configured to storeinformation. The one or more hardware processors may be configured toexecute one or more computer processing components. The one or morecomputer processing components may include one or more of a presentationcomponent, a transaction component, a minting component, a receiptcomponent, a verification component, a display component, an inputcomponent, a communication component, and/or other components.

As used herein, any association (or relation, or reflection, orindication, or correspondency) involving servers, processors, clientcomputing platforms, users, user accounts, watch faces, watch facefeatures, assets, requests, manners of usage, exchanges, challenges,offers, transactions, ownership, decentralized ledgers, responses,denials, contracts, incentives, proposals, sets of instructions,operations, determinations, distributions, transfers, presentations,interfaces, notifications, and/or another entity or object thatinteracts with any part of the system and/or plays a part in theoperation of the system, may be a one-to-one association, a one-to-manyassociation, a many-to-one association, and/or a many-to-manyassociation or “N”-to-“M” association (note that “N” and “M” may bedifferent numbers greater than 1).

As used herein, the term “receive” (and derivatives thereof) may includeactive and/or passive retrieval, determination, derivation, transfer,upload, download, submission, and/or exchange of information, and/or anycombination thereof. As used herein, the term “effectuate” (andderivatives thereof) may include active and/or passive causation of any”effect, both local and remote. As used herein, the term “determine” (andderivatives thereof) may include measure, calculate, compute, estimate,approximate, generate, and/or otherwise derive, and/or any combinationthereof.

These and other features, and characteristics of the present technology,as well as the methods of operation and functions of the relatedelements of structure and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the invention. As usedin the specification and in the claims, the singular form of ‘a’, ‘an’,and ‘the’ include plural referents unless the context clearly dictatesotherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to create a customized watch faceand retrieve the watch face to be displayed, in accordance with one ormore implementations.

FIG. 2 illustrates a method to create a customized watch face, inaccordance with one or more implementations.

FIG. 3 illustrates a method to retrieve a watch face to be displayed, inaccordance with one or more implementations.

FIG. 4 . illustrates an exemplary selection interface that may beutilized by a system to create a customized watch face, in accordancewith one or more implementations.

FIG. 5 . illustrated an exemplary watch screen displaying a watch facethat may be utilized by a system to create a customized watch face andretrieve the watch face to be displayed, in accordance with one or moreimplementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to create a customized watchface and retrieve the watch face to be displayed, in accordance with oneor more implementations. As used herein, the term “watch face” may referto a customized watch face selected and/or created by a user. As usedherein “identifier” may refer to a watch face identifier that is uniqueto a particular watch face. For example, in some implementations, anidentifier or identifying information of a watch face may include or bebased on a combination of different types of information, include butnot limited information regarding the type of watch face, the watch facefeatures, the values of watch face features, an alphanumeric string(e.g., a serial number or other text string) or other human and/ormachine readable identifier of the watch face, and/or other types ofinformation. As used herein ownership of a watch face may be tracked,recorded, and/or otherwise registered on one or more decentralizedledgers.

System 100 may include one or more server(s) 102, decentralized ledgerserver(s) 111, administration servers 115, one or more client computingplatform(s) 104, user interface(s) 125, one or more external resources126, and/or other components. As used in descriptions herein, any use ofthe term “user” may refer to users 123. Electronic storage 128 a andelectronic storage 128 b may be similar to electronic storage 128 asdescribed elsewhere in this disclosure, though included inadministration server(s) 115 and decentralized ledger server(s) 111,respectively, as depicted in FIG. 1 .

Decentralized ledger server(s) 111 may be used to implement one or moredecentralized ledger(s) 117. In some implementations, decentralizedledger(s) 117 may be maintained by distributed computing platforms (notshown in FIG. 1 ). In some implementations, a distributed computingplatform may be implemented by a set of client computing platformsand/or servers (including, for example, one or more decentralized ledgerserver(s) 111). The distributed computing platform may support a virtualmachine (not shown in FIG. 1 ). The distributed computing platformand/or the virtual machine may form a runtime environment for smartcontracts and/or other executable code. A distributed computing platformmay include electronic storage configured to store part or all ofdecentralized ledger(s) 117. The smart contracts may be stored ondecentralized ledger(s) 117 and/or another decentralized ledger. In someimplementations, the distributed computing platform may be the EOSIOplatform. In some implementations, the distributed computing platformmay be similar to or based on the EOSIO platform. In someimplementations, the distributed computing platform may be Ethereum. Insome implementations, the distributed computing platform may be similarto or based on Ethereum. In some implementations, the virtual machinemay be a decentralized virtual machine.

In some implementations, at least one of the decentralized ledger(s) 117implemented by decentralized ledger server(s) 111 is a privatepermissioned decentralized ledger. The private permissioned blockchainmay be configured to record information. The recorded information maypertain to one or more watch faces recorded on decentralized ledger(s)117. The recorded information may include ownership of the watch faces.User actions may effectuate modifications to the recorded informationpertaining to the watch faces. For example, ownership rights and/orother rights may be modified. In some implementations, a watch face maybe removed from one decentralized ledger and added or recorded onanother decentralized ledger. In some implementations, at least one ofthe decentralized ledger(s) 117 implemented by decentralized ledgerserver(s) 111 is a public decentralized ledger. The public decentralizedledger may be configured to be part of either EOSIO mainnet, Ethereummainnet, Ethereum 1.5, Ethereum 2.0, a derivative of Ethereum 2.0 thatis configured to perform transactions of Ether (ETH) between accounts,or a derivative of EOSIO that is configured to perform transactions ofEOS between different accounts.

Elements of decentralized ledger(s) 117 ledger may be grouped togetherin units that are referred to as blocks and/or nodes. For example, anindividual block may include one or more assets (e.g., watch faces)and/or one or more transactions. For example, an individual block may belinked to one or more other individual blocks. Individual blocks may belinked or chained together to form a structure of blocks and/or ahierarchy of blocks, such as, e.g., a chain of blocks. An individualblock may include one or more assets (e.g., watch faces), one or moretransactions, and/or other information. As used herein, “an individualblock including a watch face” may refer to the individual blockincluding a watch face record and/or a watch face identifier associatedwith the watch face.

As depicted in FIG. 1 , decentralized ledger server(s) 111 may includeone or more of electronic storage 128 b, processor(s) 130 b,machine-readable instructions 106 b, (node of) decentralized ledger(s)117, and/or other components. Machine-readable instructions 106 b mayinclude one or more instruction components. The instruction componentsmay include computer program components. The instruction components mayinclude one or more of a receipt component 114, a verification component116, a display component 118, and/or other instruction components. Insome implementations, an individual decentralized ledger server(s) 111may be dedicated to a particular node of a decentralized ledger(s) 117.Typically, different nodes are included in (or implemented by, or hostedby) different servers or different computer systems to increase thesafety and security of transactions on a decentralized ledger and/orblockchain. The consensus protocol used for a particular blockchain willbe harder to falsify or circumvent when the different nodes are indifferent geographical locations, on different types of computingplatforms, and/or otherwise distributed and diverse.

In some implementations, one or more decentralized ledger(s) 117implemented by decentralized ledger server(s) 111 may be publiclyaccessible. In some implementations, one or more decentralized ledgersimplemented by decentralized ledger server(s) 111 may be private and/orpermissioned. In some implementations, one or more decentralizedledger(s) 117 implemented by decentralized ledger server(s) 111 may beappend-only. In some implementations, existing blocks and/or nodes ofone or more decentralized ledger(s) 117 implemented by decentralizedledger server(s) 111 can substantially not be altered or deleted, unlessmultiple copies are altered. This is unlikely to happen provided thatthe multiple copies stored on different computing platforms, e.g., indifferent geographical locations, in accordance with the relevantconsensus protocol(s). Decentralized ledger(s) 117 may be replicated onmultiple computing platforms, preferably in multiple differentgeographical locations. Additionally, individual blocks and/or nodes maybe linked together in a manner that prevents tampering, such as, e.g.,using a hash chain and/or digital signatures. In particular, hash valuesmay be generated using fixed-output-length one-way hashing functionsthat take variable-length input, and may be effectively impossible (or,at least, computationally infeasible) to reverse. As such, a hashingfunction may provide one-way encryption. By way of non-limiting example,the hashing function may be SHA-256, BLAKE2, SHAKE256, and/or anotherhashing function. Contents of individual blocks, individual nodes,transactions, and/or assets may be digitally signed in a manner thatproves integrity and/or prevents tampering, e.g., by providingauthentication, as well as repudiation.

Server(s) 102 may be configured to communicate with one or more clientcomputing platforms 104 according to a client/server architecture and/orother architectures. Client computing platform(s) 104 may be configuredto communicate with other client computing platform(s) 104 via server(s)102 and/or according to a peer-to-peer architecture and/or otherarchitectures. User(s) 123 may access system 100 via client computingplatform(s) 104. In some implementations, system 100 and/ordecentralized ledger server(s) 111 may be configured to communicate withone or more of server(s) 102, users 123, and/or other entities and/orcomponents, e.g., through one or more network(s) 116. In someimplementations, client computing platform(s) 104 may be accessedthrough one or more user interface(s) 125. User interface(s) 125 isshown as a mobile device but may include one or more other computingdevices. User interface(s) 125 may be linked and/or associated to one ormore user watch screen(s) 127. User watch screen(s) 127 may be includein a smartwatch, a digital watch, a wearable device, a non-wearabledevice, a portable electronic device (e.g., personal digital assistance(PDA)), and/or other devices. User interface(s) 125 may be linked and/orassociated to user watch screen(s) 127 through wireless connection(e.g., Bluetooth pairing), wired connection, and/or other pairingmethods.

Server(s) 102 may include electronic storage 128, processor(s) 130,machine-readable instructions 106, and/or other components. Server(s)102 may be configured by machine-readable instructions 106.Machine-readable instructions 106 may include one or more instructioncomponents. The instruction components may include computer programcomponents. The instruction components may include one or more of apresentation component 108, a transaction component 110, a mintingcomponent 112, and/or other instruction components. Processor(s) 130 aand processor(s) 130 b may be similar to processor(s) 130 as describedelsewhere in this disclosure, though included administration server(s)115 and decentralized ledger server(s) 111, respectively, as depicted inFIG. 1 . Machine-readable instructions 106 a and machine-readableinstructions 106 b may be similar to machine-readable instructions 106as described elsewhere in this disclosure, though included inadministration server(s) 115 and decentralized ledger server(s) 111,respectively, as depicted in FIG. 1 .

Presentation component 108 may be configured to effectuate presentationof a selection interface on one or more of client computing platform(s)104 associated with a user 123. The selection interface may facilitateentry and/or selection of a watch face design by user 123. The selectioninterface may display one or more values for individual ones of watchface features. Watch face features may include one or more of hourhands, minute hands, backsplash, dials, subdials, hour markers, weatherdisplays, date displays, and/or other components capable of beingincluded in a watch face. In some implementations, particular watch facefeatures may be static and/or unchanging (e.g., hour markers). In someimplementations, watch face features may change based on one or more ofthe passage of time (e.g., hour hand, minute hand, date display), realworld events and/or real-time data (e.g. weather display), and/or otherfactors. For example, the backsplash of the watch face may include avideo, a gif, a slide show of images, and/or other moving and/or stillimages.

In some implementations, the selection interface may display the one ormore values for watch face features with an associated cost. A value fora watch face feature may indicate and/or represent a variation of color,style, format, type, and/or other aspect of the watch face feature. Forexample, a first watch face feature may be hour markers and/or anotherfeature. Hour markers may me shown as dashes, numbers, roman numerals,and/or other symbols. A first value may represent the hour markers asdashes, a second value may represent the hour markers as numbers, athird value may represent the hour markers as roman numerals, and so onand so forth. The first value, the second value, the third value, and/orother values may be included in the selection interface and/or becapable of being selected by user 123. The associated cost for anindividual value may be based on the popularity of the value, theremaining inventory of the value (i.e., the value can only be selected afixed number of times and/or by a fixed number of users), the appearanceof the value, and/or other information. In some implementations, theassociated costs of the one or more values may change based on thepopularity of the value, the remaining inventory of the value, theappearance of the value, and/or other information. The associated costsof the one or more values may change every day, every two days, every 12hours, every 2 hours, every hour, and/or other intervals of time. Insome implementations, the associated costs may be in units of dollars(USD), euros (EUR), Bitcoin (BTC), Ethereum (ETH), Tether (USDT),Dogecoin (DOGE), and/or other currencies.

In some implementations, the selection interface may display one or morepre-selected watch face designs capable of being selected by user 123for purchase. An individual watch face design may be defined by one ormore values of watch face features. The watch face design may representthe appearance of an associated watch face. For example, a watch facedesign may indicate roman numeral hour markers, a gold colored hourhand, a silver colored minute hand, a blue colored backsplash, and/orother values of watch face features. The pre-selected watch face designsmay include one or more values of watch face features that are selectedby other users 123, selected by one or more administrative users,randomly generated, and/or other methods of being selected. In someimplementations, individual ones of the pre-selected watch face designsmay include an associated cost. The associated cost of a particularpre-selected watch face designs may be based on the combined associatedcosts of the values of watch face features included in the watch facedesign. In some implementations, the associated costs of the particularpre-selected watch face design may be set by a user that created thewatch face design. In some implementations, the user 123 may purchase arandomly generated watch face design before viewing the watch facedesign and/or after viewing the watch face design. In someimplementations, the particular watch face design may only be selected(i.e., purchased) a fixed number of times. Responsive to the particularwatch face design being selected the fixed number of times, theparticular watch face design may be shown on the selection interface ashaving a sold-out status and/or not included in the selection interface.

Transaction component 110 may be configured to receive from clientcomputing platform(s) 104, a mint request to mint the watch face inaccordance with the watch face design entered and/or selected throughthe selection interface. In some implementations, the mint request mayinclude information pertaining to the watch face design, the user,and/or other information. Information pertaining to the watch facedesign may include the values of watch faces features defining the watchface design, the cost of the watch face design, and/or otherinformation. In some implementations, the mint request may be receivedfrom the client computing platform(s) 104 via one or more networks 116.The mint request may be automatically submitted to transaction component110 responsive to user 123 selecting a watch face design through theselection interface, user 123 selecting one or more action buttons onuser interface(s) 125, user 123 initiating transfer of consideration,and/or other user actions.

Transaction component 110 may be configured to, responsive to receipt ofthe mint request, effectuate a transfer of consideration from a userwallet associated with the user to an administrative wallet and/or otherwallets. The user wallet and the administrative wallet may eachcorrespond to addresses on decentralized ledger(s) 117 such that thetransfer of consideration involves a transfer of value on decentralizedledger(s) 117 from the address associated with the user wallet to theaddress associated with the administrative wallet. In someimplementations, the amount of consideration and/or value may bedetermined by the cost of the watch face design and/or the costs of thevalues of watch face features defining the watch face design. The amountof consideration and/or value may be included in the received mintrequest. The amount of consideration and/or value may further include atransfer fee, a transaction fee, a gas fee, and/or other types of feesin addition to the cost of the watch face design.

In some implementations, the user wallet may be linked to an externalwallet. The external wallet may allow the user to store and manage fundson a public decentralized ledger(s) 117. The public decentralizedledger(s) 117 may be part of either EOSIO mainnet, Ethereum mainnet,Ethereum 1.5, Ethereum 2.0, a derivative of Ethereum 2.0 that isconfigured to perform transactions of Ether (ETH) between accounts, aderivative of EOSIO that is configured to perform transactions of EOSbetween different accounts, and/or other distributed computingplatforms. In some implementations, funds may be transferred from thelinked external wallet to the user wallet. Funds transferred from thelinked external wallet to the user wallet may be in units of dollars(USD), euros (EUR), Bitcoin (BTC), Ethereum (ETH), Tether (USDT),Dogecoin (DOGE), and/or other currencies. Transferring funds from theexternal wallet to the user wallet may include a transfer fee, a gasfee, and/or other kinds of fees. The funds transferred and/or stored inthe user wallet may be used within system 100 (e.g., to buy a watchface). In some implementations, the user wallet may store funds fromtransactions made within system 100 (e.g., from selling a watch face).In some implementations, funds stored in the user wallet may only beused for transactions on decentralized ledger(s) 117 (e.g., buying,selling, or transferring watch faces). Funds stored in the user walletmay be transferred to the external wallet to be used for transactions ondecentralized ledgers outside of system 100 (e.g., buying, selling, ortransferring other digital and/or non-digital assets).

Minting component 112 may be configured to, responsive to theadministrative wallet receiving the consideration, mint the watch face.As used herein, the word “mint” may refer to performance, initiating,and/or execution of the process(es), transaction(s), procedure(s),operation(s), and/or step(s) that result in the instantiation of thewatch face, including the establishment of ownership, and definition ofappearance of the watch face. Minting the watch face may includegenerating the watch face record for the watch face in accordance withthe watch face design. Minting the watch face may further includetransforming the watch face design into a format that is readable by adevice with a watch screen and/or other methods of creating adisplayable watch face. In some implementations, minting the watch facemay include building an executable program. The executable program to betransmitted to a device capable of executing the program. In someimplementations, execution of the program by the device may display awatch face with the values of watch face features defining the watchface design on a watch screen of the device and/or other devices. Insome implementations, the watch face record may include the values ofthe watch face features that define the watch face design. In someimplementations, the watch face record may be recorded at an address ondecentralized ledger(s) 117 in a smart contract and/or other executablecode. The watch face record may include information pertaining to theminted watch face, including but not limited to the values of the watchface features defining the watch face design.

In some implementations, the watch face record may include a watch faceidentifier. The watch face identifier may be unique to the minted watchface. The identifier may include an alphanumeric string (e.g., a serialnumber or other text string) or other human and/or machine-readableidentifier of the watch face and/or other information. The identifiermay be based on the values of watch face features, the time the watchface was minted, the day the watch face was minted, and/or otherinformation. For example, a first watch face may have a first watch faceidentifier of ‘001’, a second watch face may have a second watch faceidentifier of ‘002’, a third watch face may have a third watch faceidentifier of ‘003’, and so on and so forth. The first, second, thirdwatch face identifiers, and/or other identifiers may be determined basedon the order in which the watch faces are minted. The first second,third watch face identifiers and/or other watch face identifiers may beunique, such that no two watch face identifiers are the same. In someimplementations, the first watch face and the second watch face may beminted in accordance with a first watch face design and a second watchface design, respectively. The first watch face design and the secondwatch face design may be defined by the same values of watch facefeatures (i.e., the first watch face and the second watch face have asimilar or the same appearance). The first watch face identifier and thesecond watch face identifier may still have different numerical values.In some implementations, the watch face identifier may indicate an ownerhistory for the associated watch face. For example, the watch faceidentifier may include ownership information. Ownership information mayindicate and/or identify a first owner, a second owner, a current owner,and/or other owners. By way of non-limiting example, the watch face mayhave been owned by the first owner prior to being owned by the secondowner. The watch face may have been owned by the second owner prior tobeing owned by the current owner.

In some implementations, minting the watch face may include burning thecombination of values of watch face features that define the watch facedesign. As used herein, the word “burn” may refer to recordation of thevalues of watch face features for an individual watch face such thatfuture minting of watch faces with identical values of some or all ofthe watch face features are limited or even prohibited. Burning thecombination of values may include making the combination of valuesunavailable for selection, unavailable for minting, and/or unavailablefor other actions. For example, unavailable combinations of values maynot be shown in the selection interface and/or the user may not beallowed to proceed with purchase of that watch face. In someimplementations, a combination of values may be burned after beingminted once, after being minted five times, and/or after being minted afixed number of times. In some implementations, a list of burnedcombinations may be stored in electronic storage 128, on decentralizedledger(s) 117, and/or other locations. The list of burned combinationsmay include information pertaining to the combinations of values ofwatch face features that have been burned and/or are unavailable to beminted. In some implementations, minting component 112 receiving a mintrequest may effectuate a smart contract and/or other executable code tocheck the watch face design included in the mint request against thelist of burned combinations. Responsive to the watch face design beingon the list of burned combinations, the mint request may not befulfilled. Responsive to the watch face design not being on the list ofburned combinations, the mint request may be fulfilled and/or a watchface may be minted in accordance with the watch face design.

Minting component 112 may be configured to transfer a non-fungible tokenindicating the watch face identifier to the address on the decentralizedledger(s) 117 that corresponds to the user wallet. In someimplementations, the non-fungible token may be transferredsimultaneously to the watch face record being generated. In someimplementations, transferring the non-fungible token may instruct theformation of a smart contract and/or the recording of the smart contracton decentralized ledger(s) 117 at the address corresponding to the userwallet. In some implementations, these instructions may instructdecentralized ledger(s) 117 to record and/or modify watch face records,transactions, and/or rights (e.g., ownership rights, distributionsrights, etc.). In some implementations, the non-fungible token may bestored on a blockchain. The block chain may implement decentralizedledger(s) 117 and may be capable of recording rights pertaining todigital assets (e.g., watch faces). For example, a blockchain is a typeof ledger, as well as a type of decentralized database that recordsrights pertaining to digital assets. Multiple rights may form a set ofrights or a bundle of rights that may be transferred and/or otherwiseacted on and/or operated on together. For example, rights may includeone or more of a right to use, a right to sell, a right to destroy, aright to certain types of distributions, and/or other rights. In someimplementations, the non-fungible tokens may be a type of asset. In someimplementations, the non-fungible tokens may include one or more ofsecurity tokens, utility tokens, payment tokens, initial coin offering(ICO) tokens, virtual currency tokens, crypto tokens, ERC-20 tokens,ERC-721 tokens, EOS tokens, specialized tokens, platform tokens, and/orother tokens. In some implementations, the tokens not only representvalue, but may have a specific use in a particular distributed computingplatform, e.g., in the operation of decentralized ledger(s) 117.

Receipt component 114 may be configured to receive a display request todisplay the watch face on a watch screen. The display request mayindicate user(s) 123 trying and/or wanting to display the watch face onthe watch screen. In some implementations, user 123 may submit a displayrequest through interacting with one or more user interface(s) 125,interacting with one or more devices with user watch screen(s) 127,and/or other ways. The display request may indicate the specific watchface (e.g., using the watch face identifier), a user associated with thewatch screen, a user wallet associated with the user, an address ondecentralized ledger(s) 117 associated with the user wallet, and/orother information.

Verification component 116 may be configured to, responsive to receivingthe display request, determine whether the user wallet for adecentralized ledger(s) 117 holds a non-fungible token associated withthe specific watch face. In some implementations, determining whetherthe user wallet holds a non-fungible token may include determining ifthe non-fungible token is recorded at the address associated with theuser wallet on decentralized ledger(s) 117. In some implementations, theaddress associated with the user wallet may hold one or more tokens(i.e., the user owns one or more watch faces). The non-fungible tokenmay be recorded on a smart contract and/or other executable code.Responsive to the non-fungible token being recorded at the addressassociated with the user wallet on decentralized ledger(s) 117,determine if the non-fungible token indicates the watch face identifierassociated with the watch face. In some implementations, the watch faceidentifier may be included in the display request. Responsive to thenon-fungible token indicating the watch face identifier associated withthe watch face, a determination may be made that the user has ownershipof the watch face. Responsive to the non-fungible token not indicatingthe watch face identifier associated with the watch face, adetermination may be made that the user does not have ownership of thewatch face. In some implementations, verification component 116 may beconfigured to obtain watch face rights (e.g., ownership rights,distribution rights, licensing rights, and/or other rights) for aparticular watch face, responsive to the user having ownership of theparticular watch face. In some implementations, verification component116 may be configured to access decentralized ledger(s) 117 to obtainthe watch face rights (that are recorded on decentralized ledger(s) 117,e.g., in one or more smart contracts).

Display component 118 may be configured to, responsive to the userwallet holding the non-fungible token associated with the watch face,facilitating display of the watch face on the watch screen. Facilitatingdisplay of the watch face may include initiating transmission ofinformation to the watch screen that causes the watch screen to displaythe watch face. In some implementations, information may include thewatch face design, the values of watch face features, the executableprogram, other executable code, and/or other information. In someimplementations, the watch screen may be associates to user 123 and/orassociated to the user wallet. Display component 118 may be furtherconfigured to, responsive to the user wallet not holding thenon-fungible token associated with the watch face, take no furtheraction to facilitate display of the watch face on the watch screen suchthat the watch face is not displayed on the watch screen

Input component 120 may be configured to receive user input fromadministrative users. For example, the user input may include entryand/or selection of particular information, watch face design, values ofwatch face features, watch faces, and/or any entity or object thatinteracts with any part of system 100 and/or plays a part in theoperation of system 100. For example, an administrative user may selecta particular set of watch face designs and/or values of watch facefeatures as the input for other components of system 100, such aspresentation component 108. Additionally, the administrative user mayselect a particular adjustment to be displayed by presentation component108 (e.g., increase the cost of one or more values of watch facefeatures).

Communication component 122 may be configured to facilitatecommunication and/or interaction between administration server 115 andthe rest of system 100. For example, communication component 122 maycommunicate user input received by input component 120 to othercomponents of system 100.

FIG. 4 illustrates an exemplary selection interface 400 that may be usedby a system to create a customized watch face and retrieve the watchface to be displayed in accordance with one or more implementations. Insome implementations selection interface 400 may be presented on a userinterface that is the same as or similar to user interface(s) 125 (asshown in FIG. 1 and described herein). In some implementations, a usermay view selection interface 400 through a web browser, a mobilebrowser, a mobile application, and/or other platforms. In someimplementations, the user may be required to create and/or login to auser account associated with the user to access selection interface 400.The user account may be specific to a distributed computing platformand/or system 100 (as shown in FIG. 1 and described herein). The useraccount associated with the user may also be associated with a userwallet. In some implementations, the user account and/or user wallet maystore a user's inventory. The user's inventory may include one or morewatch faces the user has purchased and/or currently owns (i.e., the userwallet holds a non-fungible token indicating the watch identifierassociated with the watch face). In some implementations, the useraccount may be used to store association to one or more watches, watchscreens, and/or other devices capable of display a watch face. The oneor more devices associated to the user account may be capable ofdisplaying one or more watch faces owned by the user.

Referring to FIG. 4 , selection interface 400 may include one or morewatch face features 40 a-b and/or other watch face features. Forexample, watch face feature 40 a may indicate selections for “Hour &Minute Hands” and watch face feature 40 b may indicate selections for“Hour Markers”. Selection interface 400 include values 42 a-e for watchface feature 40 a, values 44 a-e for watch face feature 40 b, and/orother values. In some implementations, individual ones of values 42 a-emay indicate variations of watch face feature 40 a that are capable ofbeing selected by the user and individual values of 44 a-e may indicatevariations for watch face feature 40 b. For example, value 42 a-e eachcorrespond to a different style and/or type of hour and minute handscapable of being included in a watch face design and/or a displayedwatch face. In some implementations, the user may select one or morevalues for an individual watch face features, may select no values forthe individual watch face feature, and/or may select exactly one valuefor the individual watch face feature.

In some implementations, selection of a particular value may includeclicking, touching, tapping, and/or swiping an action button associatedwith the value and/or other actions. Referring to FIG. 4 , selectioninterface 400 may include checkmarks 43, 45 and/or other checkmarksand/or components. Checkmark 43 may indicate the user has selected value42 b for watch face feature 40 a and checkmark 45 may indicate the userhas selected value 44 c for watch face feature 40 b. In someimplementations, the user may select values for one or more watch facefeatures prior to submitting a mint request. In some implementations,watch face features for which the user does not select a value may berandomly selected by the system during minting of the watch face. Insome implementations, watch face features may include hour hands, minutehands, backsplash, dials, subdials, hour markers, weather displays, datedisplays, score displays (e.g., scores for sports games), stock pricedisplays, and/or other watch face components.

FIG. 5 illustrates an exemplary watch 500 including a watch screendisplaying a watch face 54 that may be utilized by a system to create acustomized watch face and retrieve the watch face to be displayed, inaccordance with one or more implementations. Watch 500 may include awatch band 50, a watch screen 52, and/or other components. Watch screen52 may be the same as or similar to user watch screen(s) 127 (as shownin FIG. 1 ). Watch screen 52 may be held by a frame 51 and/or othercasings and/or holdings. In some implementations, watch screen 52 mayhave a square shape, a rectangular shape (as shown in FIG. 5 ), acircular shape, an oval shape, and/or other shapes. Watch screen 52 maybe configured to display a watch face 54 and/or other watch faces and/orcontent. Watch face 54 may include one or more watch face features. Thewatch face features may include one or more of hour markers 55,backsplash 56, minute hand 57, date display 58, hour hand 59, and/orother components of watch face 54. In some implementations, the valuesof the one or more watch face features may have been selected by theuser through a selection interface that is the same as or similar toselection interface 400. In some implementations, watch face 54 may beadjusted prior to being displayed on watch screen 52. Watch face 54 maybe adjusted in size, arrangement, orientations, and/or other aspects forwatch face 54 to be optimally displayed on watch screen 52. In someimplementations, watch face 54 may be adjusted by one or more computerprogram components included in system 100 (e.g., display component 118)and/or one or more compute program components included in watch 500.Adjustment of watch face 54 may be based on the size, shape, type,and/or other aspects of watch 500, watch face 54, and/or otherinformation.

Referring to FIG. 1 , user interface(s) 125 may be configured tofacilitate interaction between users 123 and system 100 and/or betweenusers 123 and client computing platform(s) 104. In some implementations,user interface(s) 125 may include one or more of a display screen,touchscreen, monitor, a keyboard, buttons, switches, knobs, levers,mouse, microphones, sensors to capture voice commands, sensors tocapture body movement, sensors to capture hand and/or finger gestures,and/or other user interface devices configured to receive and/or conveyuser input. In some implementations, one or more user interface(s) 125may be included in one or more client computing platform(s) 104. In someimplementations, one or more user interfaces 125 may be included insystem 100. In some implementations, user interface(s) 125 may be a typeof interface that facilitates the exchange of virtual items betweenusers.

Referring to FIG. 1 , in some implementations, server(s) 102, clientcomputing platform(s) 104, administration server(s) 115, decentralizedledger server(s) 111, and/or external resources 126 may be operativelylinked via one or more electronic communication links. For example, suchelectronic communication links may be established, at least in part, viaone or more network(s) 116 such as the Internet and/or other networks.It will be appreciated that this is not intended to be limiting, andthat the scope of this disclosure includes implementations in whichserver(s) 102, client computing platform(s) 104, administrationserver(s) 115, decentralized ledger server(s) 111, and/or externalresources 126 may be operatively linked via some other communicationmedia.

A given client computing platform 104 may include one or more processorsconfigured to execute computer program components. The computer programcomponents may be configured to enable an expert or user associated withthe given client computing platform(s) 104 to interface with system 100and/or external resources 126, and/or provide other functionalityattributed herein to client computing platform(s) 104. By way ofnon-limiting example, the given client computing platform(s) 104 mayinclude one or more of a desktop computer, a laptop computer, a handheldcomputer, a tablet computing platform, a NetBook, a Smartphone, a gamingconsole, and/or other computing platforms.

Administration server(s) 115 may include one or more of server(s) 102 a,processor(s) 130 a, machine-readable instructions 106 a, electronicstorage 128 a, and/or other components. Server(s) 102 a may beconfigured by machine-readable instructions 106 a. Machine-readableinstructions 106 a may include one or more instruction components. Theinstruction components may include one or more of input component 120,communication component 122, and/or other instruction components.Administration server(s) 115 may include communication lines, or portsto enable the exchange of information with a network and/or othercomputing platforms. In some implementations, administration server(s)115 may be used by one or more administrative users, e.g., to configureand/or control operation of system 100. In some implementations,administrative server(s) 115 may include or user one or more userinterfaces to receive user input and/or otherwise interact with one ormore administrative users. In some implementations, the one or moreadministrative user may be able to modify the associated costs of thevalues of watch face features, the cost of pre-selected watch facedesigns, and/or make other modifications. In some implementations, theone or more administrative users may be able to make transactions ofconsideration and/or value from and/or to the administrative wallet.

External resources 126 may include sources of information outside ofsystem 100, external entities participating with system 100, externalproviders of computation and/or storage services, and/or otherresources. In some implementations, some or all of the functionalityattributed herein to external resources 126 may be provided by resourcesincluded in system 100. In some implementations, external resources 126may include one or more blockchain oracles.

Server(s) 102 may include communication lines, or ports to enable theexchange of information with a network and/or other computing platforms.Illustration of server(s) 102 in FIG. 1 is not intended to be limiting.Server(s) 102 may include a plurality of hardware, software, and/orfirmware components operating together to provide the functionalityattributed herein to server(s) 102. For example, server(s) 102 may beimplemented by a cloud of computing platforms operating together asserver(s) 102.

Electronic storage 128 may comprise non-transitory storage media thatelectronically stores information. The electronic storage media ofelectronic storage 128 may include one or both of system storage that isprovided integrally (i.e., substantially non-removable) with server(s)102 and/or removable storage that is removably connectable to server(s)102 via, for example, a port (e.g., a USB port, a firewire port, etc.)or a drive (e.g., a disk drive, etc.). Electronic storage 128 mayinclude one or more of optically readable storage media (e.g., opticaldisks, etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 128 may include one or more virtual storageresources (e.g., cloud storage, a virtual private network, and/or othervirtual storage resources). Electronic storage 128 may store softwarealgorithms, information determined by processor(s) 130, informationreceived from server(s) 102, information received from client computingplatform(s) 104, and/or other information that enables server(s) 102 tofunction as described herein.

Processor(s) 130 may be configured to provide information processingcapabilities in server(s) 102. As such, processor(s) 130 may include oneor more of a digital processor, an analog processor, a digital circuitdesigned to process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information. Although processor(s) 130 is shown in FIG. 1 asa single entity, this is for illustrative purposes only. In someimplementations, processor(s) 130 may include a plurality of processingunits. These processing units may be physically located within the samedevice, or processor(s) 130 may represent processing functionality of aplurality of devices operating in coordination. Processor(s) 130 may beconfigured to execute components 108, 110, 112, 114, 116, 118, 120,and/or 122, and/or other components. Processor(s) 130 may be configuredto execute components 108, 110, 112, 114, 116, 118, 120, and/or 122,and/or other components by software; hardware; firmware; somecombination of software, hardware, and/or firmware; and/or othermechanisms for configuring processing capabilities on processor(s) 130.As used herein, the term “component” may refer to any component or setof components that perform the functionality attributed to thecomponent. This may include one or more physical processors duringexecution of processor readable instructions, the processor readableinstructions, circuitry, hardware, storage media, or any othercomponents.

It should be appreciated that although components 108, 110, 112, 114,116, 118, 120, and/or 122 are illustrated in FIG. 1 as being implementedwithin a single processing unit, in implementations in whichprocessor(s) 130 includes multiple processing units, one or more ofcomponents 108, 110, 112, 114, 116, 118, 120, and/or 122 may beimplemented remotely from the other components. The description of thefunctionality provided by the different components 108, 110, 112, 114,116, 118, 120, and/or 122 described below is for illustrative purposes,and is not intended to be limiting, as any of components 108, 110, 112,114, 116, 118, 120, and/or 122 may provide more or less functionalitythan is described. For example, one or more of components 108, 110, 112,114, 116, 118, 120, and/or 122 may be eliminated, and some or all of itsfunctionality may be provided by other ones of components 108, 110, 112,114, 116, 118, 120, and/or 122. As another example, processor(s) 130 maybe configured to execute one or more additional components that mayperform some or all of the functionality attributed below to one ofcomponents 108, 110, 112, 114, 116, 118, 120, and/or 122.

FIG. 2 illustrates a method 200 to create a customized watch face, inaccordance with one or more implementations. The customized watch facemay be recorded on a decentralized ledger. The customized watch face maybe capable of being displayed on a watch screen. The operations ofmethod 200 presented below are intended to be illustrative. In someimplementations, method 200 may be accomplished with one or moreadditional operations not described, and/or without one or more of theoperations discussed. Additionally, the order in which the operations ofmethod 200 are illustrated in FIG. 2 and described below is not intendedto be limiting.

In some implementations, method 200 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 200 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 200.

An operation 202 may include effectuating presentation of a selectioninterface on a client computing platform associated with a user. Theselection interface may facilitate entry and/or selection of a watchface design by the user. The watch face design may be defined by valuesof watch face features. Operation 202 may be performed by a presentationcomponent that is same as or similar to presentation component 108(shown in FIG. 1 and described herein).

An operation 204 may include receiving, from the client computingplatform, a mint request to mint the watch face in accordance with thewatch face design entered and/or selected through the selectioninterface. Operation 204 may be performed by a transaction componentthat is same as or similar to transaction component 110 (shown in FIG. 1and described herein).

An operation 206 may include effectuating, responsive to receipt of themint request, a transfer of consideration from a user wallet associatedwith the user to an administrative wallet. The user wallet and theadministrative wallet may each correspond to addresses on thedecentralized ledger such that the transfer of consideration involves atransfer of value on the decentralized ledger from the addressassociated with the user wallet to the address associated with theadministrative wallet. Operation 206 may be performed by a transactioncomponent that is same as or similar to transaction component 110 (shownin FIG. 1 and described herein).

An operation 208 may include, responsive to the administrative walletreceiving the consideration, minting the watch face. Minting the watchface may include generating a watch face record for the watch face inaccordance with the watch face design. The watch face record may includethe values of the watch face features that define the watch face design.The watch face record may include a watch face identifier. Operation 208may be performed by a minting component that is same as or similar tominting component 112 (shown in FIG. 1 and described herein).

An operating 210 may include transferring a non-fungible tokenindicating the watch face identifier to the address on the decentralizedledger that corresponds to the user wallet. Operation 210 may beperformed by a minting component that is same as or similar to mintingcomponent 112 (shown in FIG. 1 and described herein).

FIG. 3 illustrates a method 300 to retrieve a watch face to be displayedon a watch screen, in accordance with one or more implementations. Theoperations of method 300 presented below are intended to beillustrative. In some implementations, method 300 may be accomplishedwith one or more additional operations not described, and/or without oneor more of the operations discussed. Additionally, the order in whichthe operations of method 300 are illustrated in FIG. 3 and describedbelow is not intended to be limiting.

In some implementations, method 300 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 300 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 300.

An operation 302 may include receiving a display request to display thewatch face on a watch screen. The display request may indicate thespecific watch face, a user associated with the watch screen, and/orother information. Operation 302 may be performed by a receipt componentthat is same as or similar to receipt component 114 (shown in FIG. 1 anddescribed herein).

An operation 304 may include, responsive to receiving the displayrequest, determining whether a user wallet for a decentralized ledgerholds a non-fungible token associated with the specific watch face. Theuser wallet being associated with the user. Operation 304 may beperformed by a verification component that is same as or similar toverification component 116 (shown in FIG. 1 and described herein).

An operation 306 may include, responsive to the user wallet holding thenon-fungible token associated with the watch face, facilitating displayof the watch face on the watch screen. Facilitating display of the watchface may include initiating transmission of information to the watchscreen that causes the watch screen to display the watch face. Operation306 may be performed by a display component that is same as or similarto display component 118 (shown in FIG. 1 and described herein).

An operation 308 may include, responsive to the user wallet not holdingthe non-fungible token associated with the watch face, taking no furtheraction to facilitate display of the watch face on the watch screen suchthat the watch face is not displayed on the watch screen. Operation 308may be performed by a display component that is same as or similar todisplay component 118 (shown in FIG. 1 and described herein).

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. It is to beunderstood that the present technology contemplates that, to the extentpossible, one or more features of any implementation can be combinedwith features of any other implementation.

What is claimed is:
 1. A system configured to create a customized watchface, wherein ownership of the customized watch face is recorded on adecentralized ledger, and wherein the watch face is capable of beingdisplayed on a watch screen, the system comprising: one or moreprocessors configured by machine-reachable instructions to: effectuatepresentation of a selection interface on a client computing platformassociated with a user, wherein the selection interface facilitatesentry and/or selection of a watch face design by the user, and whereinthe watch face design is defined by values of watch face featuresselected by the user; receive, from the client computing platform, amint request to mint the watch face and thereby generate a new watchface in accordance with the watch face design entered and/or selectedthrough the selection interface by the user; responsive to receipt ofthe mint request, effectuate a transfer of consideration from a userwallet associated with the user to an administrative wallet, wherein theuser wallet and the administrative wallet each correspond to addresseson the decentralized ledger such that the transfer of considerationinvolves a transfer of value on the decentralized ledger from theaddress associated with the user wallet to the address associated withthe administrative wallet; and responsive to the administrative walletreceiving the consideration and further responsive to receipt of themint request: (i) mint the watch face, wherein minting the watch faceincludes initiating operations that results in instantiation of thewatch face, wherein the operations include generating a watch facerecord for the watch face in accordance with the watch face design,wherein the watch face record includes the values of the watch facefeatures that define the watch face design, and wherein the watch facerecord includes a watch face identifier, and (ii) transfer anon-fungible token indicating the watch face identifier to the addresson the decentralized ledger that corresponds to the user wallet.
 2. Thesystem of claim 1, wherein generating a watch face record for the watchface further includes burning the watch face design, such that a secondwatch face cannot be minted by the system in accordance with the samewatch face design.
 3. The system of claim 1, wherein watch face featuresinclude one or more of hour hands, minute hands, backsplash, dials,subdials, hour markers, weather displays, or date displays.
 4. Thesystem of claim 1, wherein the selection interface displays associatedcosts for individual ones of the values of watch face features, andwherein the cost of the watch face design is based on the combinedassociated costs of the values of watch face features that define thewatch face design.
 5. The system of claim 1, wherein the values of watchface features defining the watch face design is randomly generated bythe system, such that the watch face is minted and the watch face recordis generated in accordance with the randomly generated watch facedesign.
 6. A method configured to create a customized watch face,wherein ownership of the customized watch face is recorded on adecentralized ledger, and wherein the watch face is capable of beingdisplayed on a watch screen; the method comprising: effectuatingpresentation of a selection interface on a client computing platformassociated with a user, wherein the selection interface facilitatesentry and/or selection of a watch face design by the user, and whereinthe watch face design is defined by values of watch face featuresselected by the user; receiving, from the client computing platform, amint request to mint the watch face and thereby generate a new watch inaccordance with the watch face design entered and/or selected throughthe selection interface by the user; responsive to receipt of the mintrequest, effectuating a transfer of consideration from a user walletassociated with the user to an administrative wallet, wherein the userwallet and the administrative wallet each correspond to addresses on thedecentralized ledger such that the transfer of consideration involves atransfer of value on the decentralized ledger from the addressassociated with the user wallet to the address associated with theadministrative wallet; and responsive to the administrative walletreceiving the consideration and further responsive to receipt of themint request: (i) minting the watch face, wherein minting the watch faceincludes initiating operations that results in instantiation of thewatch face, wherein the operations include generating a watch facerecord for the watch face in accordance with the watch face design,wherein the watch face record includes the values of the watch facefeatures that define the watch face design, and wherein the watch facerecord includes a watch face identifier, and (ii) transferring anon-fungible token indicating the watch face identifier to the addresson the decentralized ledger that corresponds to the user wallet.
 7. Themethod of claim 6, wherein generating a watch face record for the watchface further includes burning the watch face design, such that a secondwatch face cannot be minted in accordance with the same watch facedesign.
 8. The method of claim 6, wherein watch face features includeone or more of hour hands, minute hands, backsplash, dials, subdials,hour markers, weather displays, or date displays.
 9. The method of claim6, wherein the selection interface displays associated costs forindividual ones of the values of watch face features, and wherein thecost of the watch face design is based on the combined associated costsof the values of watch face features that define the watch face design.10. The method of claim 6, wherein the values of watch face featuresdefining the watch face design is randomly generated by the system, suchthat the watch face is minted and the watch face record is generated inaccordance with the randomly generated watch face design.